Grokking Microservices Design Patterns
Rate this course
Ask Author
Contribute
Back to course home

0% completed

Vote For New Content
Introduction
Who Should Take This Course?
The Course at a Glance
Strangler Fig Pattern
Introduction
The Problem: Legacy Systems
The Strangler Pattern: A Solution
The Architecture of the Strangler Pattern
Strangler Pattern: A Detailed Example
Key Insights and Implications
Introduction to the API Gateway Pattern
Advantages of API Gateway Pattern
API Gateway Pattern: An Example
Performance Implications
System Design Example
Introduction to BFF
The Problem: Traditional Backend Models
The Architecture of the BFF Pattern
BFF Pattern: An Example
Performance Implications
System Design Examples
What is Service Discovery Pattern?
The Problem: Service Coordination in Distributed Systems
Service Discovery Pattern: A Solution
The Architecture of the Service Discovery Pattern
The Inner Workings of the Service Discovery Pattern
Service Discovery Pattern: An Example
Performance Implications and Special Considerations
System Design Examples
Security Considerations
Introduction
The Problem: The Struggles of Distributed Systems and Service Failures
The Circuit Breaker Pattern: An Effective Shield Against Cascading Failures
Circuit Breaker Pattern: An Example
Performance Implications and Special Considerations
System Design Examples
Summary
Introduction
The Problem: Failure Propagation in Distributed Systems
The Bulkhead Pattern: A Solution
The Architecture
The Inner Workings
Bulkhead Pattern: A Example
Performance Implications and Special Considerations
System Design Examples
Conclusion
Introduction
The Retry Pattern: A Solution to Unreliable External Resources
The Architecture of the Retry Pattern
Retry Pattern: An Example
Performance Implications
Use Cases and System Design Examples
Conclusion
Introduction to the Sidecar Pattern
The Problem: Monolithic Application Management
A Solution to the Monolithic Mayhem
The Architecture of the Sidecar Pattern
Sidecar Pattern: Bringing Theory to Practice with an Example
Performance Implications
System Design Examples: Bringing the Sidecar Pattern to Life
Introduction to Saga Pattern
The Problem: Traditional Transaction Models
The Saga Pattern: A Solution
The Architecture of the Saga Pattern
The Inner Workings of the Saga Pattern
Saga Pattern: A Example
Performance Implications
System Design Examples
Conclusion
Introduction
The Problem: Managing Complex Interactions in Distributed Systems
Event-Driven Architecture: A Promising Solution
The Architecture of the Event-Driven Architecture Pattern
The Inner Workings of the Event-Driven Architecture Pattern
Event-Driven Architecture Pattern: An Example
Performance Implications and Special Considerations
Use Cases and System Design Examples
Conclusion
Introduction
The Problem: Traditional CRUD Operations
CQRS Pattern: A Solution
The Architecture of the CQRS Pattern
The Inner Workings of the CQRS Pattern
CQRS Pattern: An Example
Issues, Special Considerations, and Performance Implications
System Design Examples
Introduction
The Problem: Configuration Management in a Microservices Architecture
The Solution: Configuration Externalization Pattern
Unveiling the Architecture: How Does Configuration Externalization Work?
Delving into Code: An Example
Considerations and Implications
Use Cases and Real-world Examples
Conclusion
Embrace the Future of Software Architecture
Introduction

What is Strangler Fig Pattern? It is an approach used in software development when transitioning from a monolithic architecture to a microservices architecture. The pattern is named after the strangler fig tree, which gradually grows around and eventually replaces existing trees. In the context of software engineering, it refers to the gradual process of replacing parts of a legacy system with new applications and services.

Strangler Fig Tree
Strangler Fig Tree

Imagine an ancient, humongous tree in a dense forest. This tree represents your old legacy system. One day, a new plant, the Strangler Fig, starts growing at the base of this tree. Over time, the fig grows, wrapping itself around the ancient tree. As it expands, it replaces more and more parts of the original tree until the old tree is entirely enveloped and replaced by the Strangler Fig.

This tree is a metaphor for legacy systems. These systems, often outdated yet deeply integrated, support critical business operations. They're like the old tree - rooted deeply within the organization's architecture, its many branches representing the various functions it supports. And replacing these systems can be just as daunting as replacing the old tree.

So how can we replace such deeply rooted legacy systems? There is a solution that allows you to gradually replace parts of the legacy system without causing business disruption. That solution is the Strangler Fig Pattern. It's named after the Strangler Fig, a tree that grows by gradually enveloping other trees, eventually replacing them.

What's It All About? The Strangler Fig Pattern in software design mimics the process of gradually replacing the legacy system. Instead of replacing a large, old system (the ancient tree) all at once, you build new parts (the Strangler Fig) alongside it. Gradually, the new system takes over functionalities from the old system until the old one can be safely retired.

Why Use the Strangler Fig Pattern?

With rapid technological advancement, organizations need to keep up with the latest technology to stay competitive. However, completely overhauling a legacy system can be risky and disruptive. Here's where the Strangler Pattern shines - it allows for the gradual replacement of a system, mitigating risk and minimizing disruption.

  1. Less Risky: You're not ripping out the old system in one go. So there's a safety net.
  2. Flexibility: You can prioritize which parts to replace based on urgency or business needs.
  3. No Big Bang Releases: Continuous delivery and gradual replacement mean less potential for massive failures.
  4. Smooth Transition: Users might not even notice the shift as it's gradual.
The Course at a Glance
The Problem: Legacy Systems
Mark as Completed

On this page

Why Use the Strangler Fig Pattern?